What do you dislike about Zendesk for Employee Service?
Zendesk is a solid tool, but at times it feels overly basic, with essential functionality locked behind paid marketplace apps. Features that should be standard, like setting up tasks within a ticket, often require additional subscriptions.
For example, only tickets marked as “Tasks” can be reopened at a later date. To work around this limitation for “on-hold” tickets, we had to build our own solution using their API. While there are marketplace apps that solve this, they come at an extra cost.
Using the API to create tickets has worked well for us technically, but it negatively impacts analytics. You either have to create the API key on an existing agent or pay for an additional license just to have a dedicated API user. An API user should reasonably be included at no extra cost if you already have at least one license.
Analytics in general feel unnecessarily restricted. Without paying for another agent license, reporting becomes unreliable, and it’s disappointing that custom reports are only available in the most expensive tier. Additionally we have not managed to pull analytics data via their API.
Zendesk Guide is another mixed experience. While it works well in principle, many of the features that make content organization manageable are locked behind higher-tier plans. This makes it harder to recommend as a knowledge base solution. On top of that, you’re limited to a single theme unless you pay extra.
The IT Asset Management capabilities also lack some very basic features. Asset IDs are long, random strings instead of simple incremental numbers, and more importantly, you can’t link tickets to assets. Given that tickets are Zendesk’s core functionality, this feels like a major oversight. Being able to connect tickets to assets would provide a clear and useful asset history.
Overall, Zendesk is a good tool—but with so many alternatives available, it’s hard to consider it the best or most cost-effective option. Review collected by and hosted on G2.com.